Paging priority and wireless access for non-high priority access users during wireless network congestion

ABSTRACT

A method for paging priority and wireless access which includes receiving, at a base station and from a core network, a paging message associated with a priority connection from a first user equipment device (UE) having an elevated priority status, to a second UE having a non-elevated priority status. The method further includes determining, at the base station, that non-elevated priority wireless access channels are congested, detecting, at the base station, a priority indicator within the received paging message in response to determining that the non-elevated priority wireless access channels are congested. The method further includes caching, at the base station, an identifier of the second UE in response to detecting the priority indicator in the received paging message, and establishing a wireless connection between the first UE and the second UE upon verifying that the identifier of the second UE has been cached.

BACKGROUND

Long Term Evolution (LTE) is an existing mobile telecommunicationsstandard for wireless communications. Next Generation wireless networks,such as fifth generation (5G) networks, will provide increased capacityand speed. Both LTE and 5G networks will communicate with increasingnumbers of Internet of things (IoT) and user equipment devices (UEs).Providing wireless priority services for national security and emergencypreparedness, and for public safety subscribers, can present challengesas increasing numbers of UEs may create congestion in radio accessnetworks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary wireless communicationsystem consistent with an embodiment;

FIG. 2 is a block diagram of an exemplary wireless communication systemhaving a radio access network based on an LTE standard;

FIG. 3 is a block diagram of an exemplary wireless communication systemhaving a radio access network based on a 5G standard;

FIG. 4 is a block diagram showing exemplary components of a networkdevice according to an embodiment;

FIGS. 5A-5B show a flow chart of an exemplary process for radio accessnetwork (RAN) implemented paging of a UE having non-elevated priorityduring wireless network congestion;

FIGS. 6A-6B are diagrams showing exemplary message flows within awireless communication system for a RAN implemented paging of a UEhaving non-elevated priority during wireless network congestion;

FIG. 7 shows a flow chart of an exemplary process for a combination RANand UE implementation for paging of a UE having non-elevated priorityduring wireless network congestion; and

FIGS. 8A-8B are diagrams showing exemplary message flows within awireless communication system for a RAN implemented paging of a UEhaving non-elevated priority during wireless network congestion.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. The following detailed description does not limitthe scope of the invention.

Telecommunication advancements have led to increases in the numbers andutilization of User Equipment devices (UE), including mobilecommunication handsets (e.g., smart phones) and Internet of things (IoT)devices. The increasing number of devices exchanging data with wirelessnetworks can present risks affecting the performance and availability ofdifferent services. During an emergency and/or periods of high use,access to wireless connectivity may become restricted due to congestionon the wireless channels, and thus impact public safety and/or security.

For example, network operators in the United States currently supportelevated priority services for National Security and EmergencyPreparedness (NS/EP) and Public Safety subscribers, which include voice,data and other wireless communication services. Design and featureimplementations deployed in many networks provide priority to NS/EPsubscribers over normal users in the radio access network (RAN), evolvedpacket core (EPC), and in Internet Protocol multimedia systems (IMS).The access point for the UEs, which is the RAN, is the most susceptiblepart of the system to network overload (also referred to herein as“congestion”). Although many RAN advancements improved accessibility forNS/EP subscribers during an emergency or crisis, accessibility andcapacity bottlenecks remain an issue for critical services.

Elevated priority services, which may include high priority servicessuch as, for example, wireless priority services (WPS) and Public Safetyservices, may be subscribed services for prioritized accessibility to acellular network. Third generation partnership project (3GPP) standardsand network operators define access requirements for high prioritysubscribers to gain access to a cellular network in a crisis event wherenetworks are congested. Current standards specifications, operatorrequirements and implementation present the following problem. During anemergency and network congestion scenario, when an elevated prioritysubscriber such as a high priority WPS or Public Safety subscriber,directs (e.g., terminates) a priority voice, data, or messagingconnection (e.g., a call) to a subscribed user having normal priority,the connection may fail since no priority mechanisms are in place fromthe network or the responding device.

Embodiments presented herein may address connection issues. For example,one approach may propagate priority paging information from the RAN to aUE designated as recipient UE. The UE may decode the receivedinformation, temporarily elevate its priority status to increaseaccessibility to the network and session, and respond to the RAN withradio resource control (RRC) Connection Request designating an elevatedpriority (such as, for example, an establishment cause designating“highPriorityAccess” (HPA).

In another embodiment, logic may be added to a RAN element (e.g., a basestation) which caches a parameter identifying the UE of pages havingelevated priorities (e.g., herein referred to as “priority pagingmessages”). Upon receiving priority paging messages, UEs may send RRCconnections requests in response, and if the identifier of the UEs matchone of those cached identifiers, the UEs may be admitted to the networkregardless of their Establishment cause (such as, for example“emergency,” “highPriorityAccess,” “mt-Access,” “mo-Signalling,” and/or“mo-Data”).

FIG. 1 is a diagram illustrating an exemplary wireless communicationsystem 100 consistent with an embodiment. As shown in FIG. 1,environment 100 may include user equipment devices (UEs) 110-1 to 110-N(referred to herein plurally, but not necessarily collectively or intheir entirety, as “UEs 110”, and individually as “UE 110-x”), a basestation (BS) 120, a core network (CN) 130, and an IP multimediasubsystem (IMS) 140. UEs 110 may communicate over wireless channels withBS 120 via RAN 115 using any type of known cellular network, such as,for example, LTE, LTE Advanced, 5G, etc. UEs 110 may exchange data withCN 130 via BS 120 through one or more dedicated channels having varyinglevels of priority. In the example shown in FIG. 1, UE 110-1 may have anelevated priority status (e.g., “highPriorityAccess” (HPA)) and UEs110-2 through 110-N may have a non-elevated priority status (e.g.,non-HPA). CN 130 may further exchange data with IMS 140 via a backhaulnetwork (not shown). Accordingly, through BS 120 and CN 130, UEs 110 mayobtain access to IMS 140 for exchanging IP data using any applicationprotocol, such as SIP.

UEs 110 may be in various states of connection with BS 120 via RAN 115.For example, some UEs 110 may have radio connections in an active state(e.g., radio resource connection (RRC) active) where data may beexchanged, and other UEs 110 may have idle radio connections (e.g., RRCidle). Thus, when in RRC idle mode, UE 110 does not have an activecommunication path to RAN 115 or CN 130. Paging procedures address thisissue by alerting or paging the idle UE 110 to re-establish a radioconnection and bearer path with the wireless network. The 3GPP TechnicalSpecification 36.413 defines an attribute for CN 130 elements, such asthe 4G mobility management entity (MME) or 5G access and mobilitymanagement function (AMF) used to prioritize a paging message of an RRCidle UE. Within a paging message sent from CN 130 to RAN 115, a pagingpriority parameter may indicate the priority of the paging message. Thepaging priority parameter may have, for example, eight defined levels.Critical subscribers (also referred to herein as “elevated prioritysubscribers”) such as, for example, first responders, public utilities,law enforcement or other government entities can utilize availablecritical priority services (such as, for example, mission critical pushto talk (MC-PTT), data, messaging and/or multimedia priority services(MPS)) on a subscribed basis. In conventional networks, paging priorityonly works as expected if the originating and terminating parties areboth subscribed to critical services. When an originating criticalsubscriber calls a non-priority subscriber, a paging message whichoriginates at the MME or AMF will still have the paging priorityindicator. However, due to current standards and implementation, thebase station 120 removes the paging priority indicator before sendingthe paging message to the non-elevated priority UE 110. During networkcongestion, critical subscribers in the field may be required tocommunicate to non-elevated priority (e.g., “normal”) subscribers. Whenan elevated priority subscribed user originates an elevated prioritycall to an RRC-idle Public/normal non-elevated user, the elevatedpriority paging message may be delivered. In response to the pagingmessage, the non-elevated priority user attempts to connect to thecongested cell and the call will likely fail since the RAN is in acongested state. This results in a communication failure for a criticalservice user such as WPS or First Responder agents in the field.

Embodiments described herein may address connection issues with thefollowing approaches. In one embodiment, a capability may be added to aRAN element (e.g., base station 120) which provides for caching aparameter identifying UE 110 for paging messages having elevatedpriorities (e.g., herein referred to as “priority paging messages”).Upon receiving priority paging messages, UEs 110 may send RRCconnections requests in response, and if the identifier of the UEs 110match those cached in base station 120, UEs 110 may be admitted to thenetwork regardless of their Establishment cause. In another embodiment,the RAN (e.g., base station 120) may propagate paging information to UE110 which is the recipient of the paging message. Upon receiving thepaging message, UE 110 may decode the received information, temporarilyelevate the priority status of UE 110 to increase accessibility to thenetwork and session, and respond to the RAN with an RRC ConnectionRequest designating an elevated priority (such as, for example, anestablishment cause designating “highPriorityAccess” (HPA)).

Further referring to FIG. 1, UEs 110 may include any device withlong-range (e.g., cellular or mobile wireless network) wirelesscommunication functionality. For example, UEs 110 may include a handheldwireless communication device (e.g., a mobile phone, a smart phone, atablet device, etc.); a wearable computer device (e.g., a head-mounteddisplay computer device, a head-mounted camera device, a wristwatchcomputer device, etc.); a laptop computer, a tablet computer, or anothertype of portable computer; a desktop computer, or a digital media player(e.g., Apple TV®, Google Chromecast®, Amazon Fire TV®, etc.); a smarttelevision; a portable gaming system; a global positioning system (GPS)device; a home appliance device; a home monitoring device; and/or anyother type of computer device with wireless communication capabilitiesand a user interface. UE 110 may also include any type of customerpremises equipment (CPE) such as a set top box, a wireless hotspot (e.g.an LTE or 5G wireless hotspot), a femto-cell, etc. UE 110 may includecapabilities for voice communication, mobile broadband services (e.g.,video streaming, real-time gaming, premium Internet access etc.), besteffort data traffic, and/or other types of applications.

In some implementations, UEs 110 may communicate usingmachine-to-machine (M2M) communication, such as machine-typecommunication (MTC), a type of M2M communication standardized by the3^(rd) Generation Partnership Project (3GPP), and/or another type of M2Mcommunication. UEs 110 may be embodied as IoT devices, which may includehealth monitoring devices, asset tracking devices (e.g., a systemmonitoring the geographic location of a fleet of vehicles, etc.),sensors (e.g., utility sensors, traffic monitors, etc.)

BS 120 and CN 130 provide access to IMS 140 for providing multimedia IPservices to UEs 110. Such services may include mobile voice service(e.g., various forms of voice over Internet Protocol (VoIP)), shortmessage service (SMS), multimedia message service (MMS), multimediabroadcast multicast service (MBMS), Internet access, cloud computing,and/or other types of data services. While not shown, BS 120 and CN 130may further provide additional access to a wide area network (WAN) notshown for other IP and/or non-IP data delivery (NIDD) services.

In some implementations, BS 120 and CN 130 may include Long TermEvolution (LTE) and/or LTE Advance (LTE-A) capability, where BS 120 mayinclude as an eNodeB, and CN 130 may include as an evolved packet core(EPC) network. Alternatively, in other implementations, BS 120 and CN130 may include 5G access capability, where BS 120 may include a nextgeneration Node B (gNodeB), and CN 130 may serve as a 5G packet core (5GPC) network. Such implementations may include functionality such as 5Gnew radio (NR) base stations; carrier aggregation; advanced or massivemultiple-input and multiple-output (MIMO) configurations; HeterogeneousNetworks (HetNets) of overlapping small cells and macrocells;Self-Organizing Network (SON) functionality; MTC functionality, such as1.4 MHz wide enhanced MTC (eMTC) channels (also referred to as categoryCat-M1), Low Power Wide Area (LPWA) technology such as Narrow Band (NB)IoT (NB-IoT) technology, and/or other types of MTC technology.

IMS 140 may include one or more devices, such as computer devices,databases, and/or server devices, that facilitate IP data deliveryservices. Such services may include supporting IoT applications such asalarms, sensors, medical devices, metering devices, smart home devices,wearable devices, retail devices, etc. Other services may includesupporting other communications applications (e.g., SMS, etc.),automotive applications, aviation applications, etc. IMS 140 maycommunicate with UEs 110 over BS 120 and CN 130 using IP and/or non-IPbearer channels.

Although FIG. 1 shows exemplary components of wireless communicationsystem 100, in other implementations, wireless communication system 100may include fewer components, different components, differently arrangedcomponents, or additional components than depicted in FIG. 1.Additionally or alternatively, one or more components of wirelesscommunication system 100 may perform functions described as beingperformed by one or more other components of wireless communicationsystem 100.

FIG. 2 is a block diagram of an exemplary wireless communication system200 based on the LTE standard. Wireless communication system 200 mayinclude an LTE network with an evolved Packet Core (ePC) 210 and eNodeB220 (corresponding, for example, to CN 130 and BS 120, respectively). UE110 and eNodeB 220 may exchange data over a radio access technology(RAT) based on LTE air channel interface protocols. In the embodimentshown in FIG. 2, EPC 210 may operate in conjunction with an evolvedUniversal Mobile Telecommunications System (UMTS) Terrestrial Network(eUTRAN) that includes at least one eNodeB 220. Wireless communicationsystem 200 may further include an IP network and/or a non-IP network.Such networks may be embodied separately or included in a backhaulnetwork and/or in a wide area network (not shown). EPC 210 may also beconnected to subsystems in IMS 140.

EPC 210 may include one or more devices that are physical and/or logicalentities interconnected via standardized interfaces. EPC 210 provideswireless packet-switched services and wireless packet connectivity toUEs 110 to provide, for example, data, voice, and/or multimediaservices. EPC 210 may further include a mobility management entity (MME)250, a serving gateway (SGW) 260, a home subscriber server (HSS) 270, apacket data network gateway (PGW) 280, and a Policy and Charging RulesFunction (PCRF) 290. It is noted that FIG. 2 depicts a representativenetworking system 200 with exemplary components and configuration shownfor purposes of explanation. Other embodiments may include additional ordifferent network entities in alternative configurations than which areexemplified in FIG. 2. For example, IMS 140 may communicate with ePC210, and include various call session control functions (CSCF), whichmay include interrogating/serving CSCF 292 (I/S CSCF), and proxy CSCF295 (P-CSCF). I/S-CSCF 292 and P-CSCF 295 may exchange information usingan Mw interface 245 using session initiation protocol (SIP).

Further referring to FIG. 2, eNodeB 220 may include one or more devicesand other components having functionality that allows UE 110 towirelessly connect via the RAT of eNodeB 220. eNodeB 220 may interfacewith ePC 210 via a S1 interface, which may be split into a control planeS1-AP interface 224 and a data plane S1-U interface 225. EnodeB 220 mayinterface with MME 250 via S1-AP interface 224, and interface with SGW260 via S1-U interface 225. S1-U interface 225 may be implemented, forexample, using GTP. S1-AP interface 224 may be implemented, for example,with a protocol stack that includes a Non-Access Stratum (NAS) protocoland/or Stream Control Transmission Protocol (SCTP).

MME 250 may implement control plane processing for both the primaryaccess network and the secondary access network. For example, througheNodeB 220, MME 250 may implement tracking and paging procedures for UE110, may activate and deactivate bearers for UE 110, and mayauthenticate a user of UE 110 to provide normal coverage service foroperating in normal UE device mode. MME 250 may also select a particularSGW 260 for a particular UE 110. MME 250 may interface with other MMEs(not shown) in ePC 210 and may send and receive information associatedwith UEs 110, which may allow one MME 250 to take over control planeprocessing of UEs 110 serviced by another MME 250, if the other MMEbecomes unavailable.

MME 250 may communicate with SGW 260 through an S11 interface 235. S11interface 235 may be implemented, for example, using GTPv2. S11interface 235 may be used to create and manage a new session for aparticular UE 110. S11 interface 235 may be activated when MME 250 needsto communicate with SGW 260, such as when the particular UE 110 attachesto ePC 210, when bearers need to be added or modified for an existingsession for the particular UE 110, when a connection to a new PGW 280needs to be created, or during a handover procedure (e.g., when theparticular UE 110 needs to switch to a different SGW 260).

SGW 260 may provide an access point to and from UE 110, may handleforwarding of data packets for UE 110, and may act as a local anchorpoint during handover procedures between eNodeBs 220. SGW 260 mayinterface with PGW 280 through an S5/S8 interface 247. S5/S8 interface245 may be implemented, for example, using GTP.

HSS 270 may store information associated with UE 110 and/or informationassociated with users of UE 110. For example, HSS 270 may store userprofiles that include registration, authentication, and accessauthorization information. MME 250 may communicate with HSS 270 throughan S6a interface 265. S6a interface 265 may be implemented, for example,using a Diameter protocol. HSS 270 may communicate with I/S CSCF 292within IMS 140 via a Cx interface 267. Cx interface 257 may be implementusing a Diameter protocol.

PGW 280 may function as a gateway to IMS 140 through an SGi interface255. IMS 140 may provide various services (e.g., IP over multimediaservices such over the top voice services) to UE 110. A particular UE110, while connected to a single SGW 260, may be connected to multiplePGWs 280, one for each packet network with which UE 110 communicates.PGW 280 may exchange information with P-CSCF 295 using the SGi interface255 based on TCP/IP.

Alternatively, UE 110 may exchange data with WAN 140 though a WiFiwireless access point (WAP) (not shown). The WiFi WAP may be part of alocal area network, and access WAN 140 through a wired connection via arouter. Alternatively, the WiFi WAP may be part of a mesh network (e.g.,802.11s). The WiFi WAP may operate in accordance with any type of WiFistandard (e.g., any IEEE 802.11x network, where x=a, b, c, g, and/or n),and/or include any other type of wireless network technology forcovering larger areas, and may include a mesh network (e.g., IEEE802.11s) and/or or a WiMAX IEEE 802.16. The WiFi WAP may also be part ofa wide area network (WiMAX) or a mesh network (802.11s).

PCRF 290 provides policy control decision and flow-based chargingcontrol functionalities. PCRF 290 may provide network control regardingservice data flow detection, gating, QoS and flow based charging, etc.PCRF 290 may determine how a certain service data flow shall be treated,and may ensure that user plane traffic mapping and treatment are inaccordance with a user's subscription profile based, for example, on aspecified quality of service (QoS) class identifier (QCI). PCRF 290 maycommunicate with PGW 280 using a Gx interface 280. Gx interface 280 maybe implemented, for example, using a Diameter protocol. PCRF 290 mayalso interface to P-CSCF 295 using an Rx interface 245. The Rx interfacemay be used to exchange charging information via a Diameter protocol.

While FIG. 2 shows exemplary components of networking system 200, inother implementations, networking system 200 may include fewercomponents, different components, differently arranged components, oradditional components than depicted in FIG. 2. Additionally oralternatively, one or more components of networking system 200 mayperform functions described as being performed by one or more othercomponents of networking system 200.

FIG. 3 is a block diagram of an exemplary wireless communication system300 having a radio access network based on a 5G standard. Wirelesscommunication system 300 may include an 5G network with a 5G Core (5GC)325, gNodeB 310 (corresponding, for example, to CN 130 and BS 120,respectively), UE 110, and IMS 140. UE 110 and gNodeB 310 may exchangedata over a radio access technology (RAT) based on 5G air channelinterface protocols. Wireless communication system 300 may furtherinclude an Internet Protocol (IP) network and/or a non-IP network, whichmay be embodied separately or included in a backhaul network and/or in awide area network (not shown). 5GC 325 may also be connected tosubsystems in IMS 140. IMS 140 may include various CSCFs, I/S-CSCF 292and/or P-CSCF 295, which may exchange information via Mw interface 245using SIP.

5GC 325 may include an Access and Mobility Function (AMF) 320, a UserPlane Function (UPF) 330, a Session Management Function (SMF) 340, anApplication Function (AF) 350, a Unified Data Management (UDM) 352, aPolicy Control Function (PCF) 354, a Network Repository Function (NRF)356, an Authentication Server Function (AUSF) 358, and a Network SliceSelection Function (NSSF) 360. While FIG. 3 depicts a single gNodeB 310,AMF 320, UPF 330, SMF 340, AF 350, UDM 352, PCF 354, NRF 356, AUSF 358,and/or NSSF 360 for exemplary illustration purposes, in practice, FIG. 3may include multiple gNodeBs 310, AMFs 320, UPFs 330, SMFs 340, AFs 350,UDMs 352, PCFs 354, NRFs 356, AUSFs 358, and NSSFs 360.

GNodeB 310 may include one or more device, components, and/orfunctionality that enable UE 110 to wirelessly connect to 5GC 325 using5G NR RAT. For example, gNodeB 310 may include one or more cells, witheach cell site equipment including a wireless transceiver with anantenna array configured for millimeter-wave wireless communication.GNodeB 310 may implement one or more RAN slices to partition 5GC 325.GNodeB 310 may communicate with AMF 320 using an N2 interface 322 andcommunicate with UPF 330 using an N2 interface 332.

AMF 320 may perform registration management, connection management,reachability management, mobility management, lawful intercepts, ShortMessage Service (SMS) transport between UE 110 and an SMS function (notshown in FIG. 3), session management messages transport between UE 110and SMF 340, access authentication and authorization, location servicesmanagement, functionality to support non-3GPP access networks, and/orother types of management processes. In some implementations, AMF 320may implement some or all of the functionality of managing RAN slices ingNodeB 310. AMF 320 may be accessible by other function nodes via a Namfinterface 324.

UPF 330 may maintain an anchor point for intra/inter-RAT mobility,maintain an external Packet Data Unit (PDU) point of interconnect to adata network (e.g., WAN), perform packet routing and forwarding, performthe user plane part of policy rule enforcement, perform packetinspection, perform lawful intercept, perform traffic usage reporting,enforce QoS policies in the user plane, perform uplink trafficverification, perform transport level packet marking, perform downlinkpacket buffering, send and forward an “end marker” to a Radio AccessNetwork (RAN) node (e.g., gNodeB 310), and/or perform other types ofuser plane processes. UPF 330 may communicate with SMF 340 using an N4interface 334 and connect to WAN 140 using an N6 interface 336. UPF 330may communicate with P-CSCF 295 using an N6 interface 370.

SMF 340 may perform session establishment, modification, and/or release,perform IP address allocation and management, perform Dynamic HostConfiguration Protocol (DHCP) functions, perform selection and controlof UPF 330, configure traffic steering at UPF 330 to guide traffic tothe correct destination, terminate interfaces toward PCF 354, performlawful intercepts, charge data collection, support charging interfaces,control and coordinate of charging data collection, termination ofsession management parts of network access stratum (NAS) messages,perform downlink data notification, manage roaming functionality, and/orperform other types of control plane processes for managing user planedata. SMF 340 may be accessible via an Nsmf interface 342.

AF 350 may provide services associated with a particular application,such as, for example, application influence on traffic routing,interacting with a policy framework for policy control, and/or othertypes of applications. AF 350 may be accessible via a Naf interface 362.

UDM 352 may maintain subscription information for UE 110, managesubscriptions, generate authentication credentials, handle useridentification, perform access authorization based on subscription data,perform network function registration management, maintain serviceand/or session continuity by maintaining assignment of SMF 340 forongoing sessions, support SMS delivery, support lawful interceptfunctionality, and/or perform other processes associated with managinguser data. UDM 352 may be accessible via a Nudm interface 364. UDM 352may communicate with I/S-CSCF 290 through a Cx interface 374. Cxinterface 374 may exchange data pertaining to, for example, userregistration, authentication, location, and profile information.

PCF 354 may support policies to control network behavior, provide policyrules to control plane functions (e.g., to SMF 340), access subscriptioninformation relevant to policy decisions, execute policy decisions,and/or perform other types of processes associated with policyenforcement. PCF 354 may be accessible via Npcf interface 366. PCF 354may specify QoS policies based on QoS flow identity (QFI) consistentwith 5G network standards. PCF 354 may communicate with P-CSCF 295 viaN5 interface 372. N5 interface 372 may exchange data pertaining to forexample, quality of service (QoS) information, authorization, andretention priority information.

NRF 356 may support a service discovery function and maintain a profileof available network function (NF) instances and their supportedservices. An NF profile may include an NF instance identifier (ID), anNF type, a Public Land Mobile Network (PLMN) ID associated with the NF,a network slice ID associated with the NF, capacity information for theNF, service authorization information for the NF, supported servicesassociated with the NF, endpoint information for each supported serviceassociated with the NF, and/or other types of NF information. NRF 356may be accessible via an Nnrf interface 368.

AUSF 358 may be located within the home network and provideauthentication services for UE 110 and other security related functionsfor 5GC 325. AUSF 358 may authenticate UE 110 using materials obtainedthrough an Nudm authentication service while using the method specifiedby the service consumer. Additionally, AUSF 358 may compute keys used toprotect the Steering Information List when requested. AUSF 358 may usean Nausf 370 service interface.

NSSF 360 may select a set of network slice instances to serve aparticular UE 110, determine network slice selection assistanceinformation (NSSAI), determine a particular AMF 320 to serve aparticular UE 110, and/or perform other types of processes associatedwith network slice selection or management. In some implementations,NSSF 360 may implement some or all of the functionality of managing RANslices in gNodeB 310. NSSF 360 may be accessible via Nnssf interface372.

Although FIG. 3 shows exemplary components of 5GC 325, in otherimplementations, 5GC 325 may include fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 3. Additionally or alternatively, one or morecomponents of 5GC 325 may perform functions described as being performedby one or more other components of 5GC 325. For example, 5GC 325 mayinclude additional function nodes not shown in FIG. 3, such as anAuthentication Server Function (AUSF), a Non-3GPP Interworking Function(N3IWF), a Unified Data Repository (UDR), an Unstructured Data StorageNetwork Function (UDSF), an SMS function (SMSF), a 5G Equipment IdentityRegister (5G-EIR) function, a Location Management Function (LMF), aSecurity Edge Protection Proxy (SEPP) function, and/or other types offunctions. Furthermore, while particular interfaces have been describedwith respect to particular function nodes in FIG. 3, additionally oralternatively, 5GC 325 may include a reference point architecture thatincludes point-to-point interfaces between particular function nodes.

FIG. 4 is a block diagram showing exemplary components of a networkdevice 400 according to an embodiment. Network device 400 may includeone or more network elements illustrated in FIGS. 2-3 such as, forexample, a UE device 110, a base station 120 (e.g., eNodeB 220 and/orgNodeB 310), elements in ePC 210, elements in 5GC 325, etc. In someembodiments, there may be a plurality of network devices 400 providingfunctionality of one or more network elements. Alternatively, oncenetwork device 400 may perform the functionality of any plurality ofnetwork elements. Network device 400 may include a bus 410, a processor420, a memory 430, storage device 440, a network interface 450, inputdevice 460, and an output device 470.

Bus 410 includes a path that permits communication among the componentsof network device 400. Processor 420 may include any type of single-coreprocessor, multi-core processor, microprocessor, latch-based processor,and/or processing logic (or families of processors, microprocessors,and/or processing logics) that interprets and executes instructions. Inother embodiments, processor 420 may include an application-specificintegrated circuit (ASIC), a field-programmable gate array (FPGA),and/or another type of integrated circuit or processing logic. Forexample, processor 420 may be an x86 based CPU, and may use anyoperating system, which may include varieties of the Windows, UNIX,and/or Linux operating systems. Processor 420 may also use high-levelanalysis software packages and/or custom software written in anyprogramming and/or scripting languages for interacting with othernetwork entities.

Memory 430 may include any type of dynamic storage device that may storeinformation and/or instructions, for execution by processor 420, and/orany type of non-volatile storage device that may store information foruse by processor 420. For example, memory 430 may include a randomaccess memory (RAM) or another type of dynamic storage device, a readonly memory (ROM) device or another type of static storage device,and/or a removable form of memory, such as a flash memory. Storagedevice 440 may include any type of on-board device suitable for storinglarge amounts of data, and may include one or more hard drives, solidstate drives, and/or various types of redundant array of independentdisks (RAID) arrays. In an embodiment, storage device 440 may storeprofile data associated with UEs 110.

Network interface 450 may include a transceiver that enables networkdevice 150 to communicate with other devices and/or systems in networkenvironment 100. Network interface 450 may be configured to exchangedata over wired communications (e.g., conductive wire, twisted paircable, coaxial cable, transmission line, fiber optic cable, and/orwaveguide, etc.), or a combination of wired and wireless communications.In other embodiments, network interface 450 may interface with otherdevices using a wireless communications channel, such as, for example,radio frequency (RF), infrared, and/or visual optics, etc. Networkinterface 450 may include a transmitter that converts baseband signalsto RF signals and/or a receiver that converts RF signals to basebandsignals. Network interface 450 may be coupled to one or more antennasfor transmitting and receiving RF signals. Network interface 450 mayinclude a logical component that includes input and/or output ports,input and/or output systems, and/or other input and output componentsthat facilitate the transmission/reception of data to/from otherdevices. For example, network interface 450 may include a networkinterface card (e.g., Ethernet card) for wired communications and/or awireless network interface (e.g., a WiFi) card for wirelesscommunications. Network interface 450 may also include a universalserial bus (USB) port for communications over a cable, a Bluetooth®wireless interface, a radio frequency identification device (RFID)interface, a near field communications (NFC) wireless interface, and/orany other type of interface that converts data from one form to anotherform.

As described below, network device 400 may perform certain operationsrelating to performing uplink congestion control based on SIP messaging.Network device 400 may perform these operations in response to processor420 executing software instructions contained in a computer-readablemedium, such as memory 430 and/or storage device 440. The softwareinstructions may be read into memory 430 from another computer-readablemedium or from another device. The software instructions contained inmemory 430 may cause processor 420 to perform processes describedherein. Alternatively, hardwired circuitry may be used in place of, orin combination with, software instructions to implement processesdescribed herein. Thus, implementations described herein are not limitedto any specific combination of hardware circuitry and software. In anembodiment, the software instructions and/or hardware circuitry mayperform the process exemplified by the flow charts shown in FIGS. 5A-5B,and 7 and the signal flows shown in FIGS. 6A-6B, and FIGS. 8A-8B.

Although FIG. 4 shows exemplary components of network device 400, inother implementations, network device 400 may include fewer components,different components, additional components, or differently arrangedcomponents than depicted in FIG. 4.

FIGS. 5A-5B show a flow chart of an exemplary process 500 for RANimplemented paging of one of UEs 110-2 through 110-N having non-elevatedpriority during wireless network congestion. For ease of explanation,the following descriptions of FIGS. 5A through 8B will refer to UE 110-2from the group of UEs 110-2 through 110-N as having a non-elevatedpriority status (e.g., non-HPA). However, any one of UEs 110-2 through110-N may be the recipient of a priority paging message originating fromUE 110-1, as set forth below. In an embodiment, process 500 may beperformed by a network device 400 using on processor 420. In anembodiment, network device 400 may be base station 120.

Initially, network device 400 may receive, from CN 130, a paging messageassociated with a priority connection from elevated priority UE 110-1(Block 505). The paging message may be directed to a non-elevatedpriority UE 110-2. In an embodiment, UE 110-1 may be associated with anelevated priority service, and the paging message may be a prioritypaging message. The elevated priority service may be a high priorityservice that can include a wireless priority service (WPS), a publicsafety service, a national security service, an emergency preparednessservice, etc. The paging message originating from the priorityconnection established by UE 110-1 may include a priority pagingmessage.

Network device 400 may determine whether non-elevated priority (e.g.,normal priority) wireless access channels are congested (Block 510). Inan embodiment, determining congestion may include ascertaining whether athreshold for a non-elevated priority bearer channel has been exceeded.Additionally or alternatively, congestion may be ascertained bydetermining whether resource usage associated with a radio resourcecontrol layer have been exhausted or exceeded. If in Block 510 networkdevice 400 determines that the non-elevated priority wireless accesschannels are not congested (Block 510—no), network device 400 may admitUE 110-2 for non-elevated priority access (Block 515).

If in Block 510 network device 400 determines that the non-elevatedpriority wireless access channels are congested (Block 510—yes), networkdevice 400 may then proceed to Block 520. In block 520, network device400 may detect a priority indicator in the paging message received fromCN 130. If the priority indicator is detected in Block 520 (Block520—yes), network device 400 may cache the identifier of the UE 110-2,which may be specified in the paging message received from CN 130 (Block525). In an embodiment, the identifier of UE 110-2 may be, for example,specified as the Serving Temporary Mobile Subscriber Identity (S-TMSI)of UE 110-2. Once the identifier of UE 110-2 is cached, network device400 will forward the paging message to UE 110-2 (Block 530).Alternatively, if network device 400 does not detect the priorityindicator of the paging message in Block 520, the identifier parameterof UE 110-2 may not be cached, and the paging message may be forwardedto UE 110-2 (Block 530). UE 110-2 will process the paging message, andin response, generate and send a connection request back to networkdevice 400. In an embodiment, UE 110-2 may send a radio resource control(RRC) connection request.

Network device 400 may receive the connection request from UE 110-2(Block 535), and identify whether the received connection request is anon-priority connection request (Block 540). If network device 400identifies a non-priority connection request, network device 400 willadmit UE 110-2 to the RAN 115 with a non-priority status (Block 545).Alternatively, if in Block 540 network device 400 determines thereceived connection request is a priority request (Block 540—yes), thennetwork device 400 may determine if the UE identifier was previouslycached (Block 550). If the UE identifier was previously cached (Block550—yes), then network device 400 will admit UE 110-2 with an elevatedpriority status (560). If the UE 110-2 identifier was not cached (Block550—no), the UE 110-2 will be rejected (not admitted to RAN 115) orreleased (Block 555). When UE 110-2 is granted priority status, the RRCconnection request and associated bearers are granted elevated priorityfor the duration of the session.

FIGS. 6A-6B are diagrams showing exemplary message flows within awireless communication system 200 and/or 300 for RAN implemented pagingof a UE having non-elevated priority during wireless network congestion.The message flow diagrams show network components which may correspondto both LTE and 5G network standards. The LTE components are shown withthe label “2XX” and the 5G components are shown with the label “3XX.”For example, as shown in FIGS. 6A-6B, the base station elements areshown as “eNode 220/gNode 310,” the mobility managers are shown as “MME250/AMF 320,” etc.

In FIG. 6A, flow diagram 600 initially shows UE 110-1 and UE 110-2 ashaving completed an attachment and registration procedure and are bothin an RCC Idle state (602). In the embodiment shown in FIG. 6A, UE 110-2is associated with a non-HPA status (i.e., a non-elevated or “normal”priority status), and UE 110-1 is associated with an HPA status (i.e.,an elevated priority status). UE 110-1 may originate a priorityconnection to UE 110-2 during a period of congestion on the RAN (604). Apriority connection request is sent from UE 110-1 to PGW 280/SGW 260 orUPF 330. The connection request may be provided via IMS 140. PGW 280/SGW260 or UPF 330 may then send a downlink data notification to MME 250 orAMF 320 (606). The downlink data notification may also include a messageor signal for a high priority allocation and retention priority (ARP)status. MME 230/AMF 320 may generate and send to eNB 220/gNB 310 apaging message with a paging priority indicator (indicating an elevatedpriority), and an s-TMSI value indicating the identity of UE 110-2(608). Upon receiving the paging message (608), eNB 220/gNB 310 mayidentify the paging message as high priority (Block 610), detect RANcongestion (Block 612), and in response, cache the identifier (e.g.,s-TMSI) of UE 110-2 as HPA (e.g., elevated priority).

Further referring to FIG. 6B, eNB 230/gNB 310 may send a paging messageto UE 110-2 (620). In response, UE 110-2 may send an RRC connectionrequest back to eNB 220/gNB 310 (622). ENB 220/gNB 310 may check a localcache for a match of the identifier (e.g., s-TMSI value) associated withUE 110-2 as provided in the RRC connection request. When a match isfound, eNB 220/gNB 310 may recognize UE 110-2 as having an HPA status(e.g., elevated priority) and admit UE 110-2 to RAN 115, and establish abearer for data communication (624). Once the bearer is established byMME 230/AMF 320, UE 110-2 may establish priority communications with UE110-1 (628).

FIG. 7 shows a flow chart of an exemplary process 700 for a combinationRAN and UE implementation for paging of a UE having non-elevatedpriority during wireless network congestion. In an embodiment, process700 may be performed by a network device 400 using processor 420, wherenetwork device 400 may be base station 120.

Initially, network device 400 may receive, from CN 130, a paging messageassociated with a priority connection from elevated priority UE 110-1(Block 705). The paging message may be directed to non-elevated priorityUE 110-2. As noted in FIG. 5A above, UE 110-1 may be associated with anelevated priority service, and the paging message may be a prioritypaging message. The elevated priority service may be a high priorityservice that can include a WPS, a public safety service, a nationalsecurity service, an emergency preparedness service, etc. The pagingmessage sent by UE 110-1 may include a priority paging message.

Network device 400 may determine whether the paging message includes apaging priority indicator (designating an elevated priority, such as,for example, HPA) (710). If network device 400 determines pagingmessages does not have a paging priority indicator (Block 710—no),network device 400 may send the paging message to UE 110-2 (Block 715).Alternatively, if network device 400 determines the paging messageincludes a paging priority indicator (Block 710—yes), network device 400may set a paging priority parameter withing the paging message (720). Inan embodiment, setting the paging priority parameter may be performed bysetting a single bit in the paging message.

Network device 400 may then send the priority paging message to UE 110-2via RAN 115 (725). In response, UE 110-2 may generate and send an RRCconnection request to network device 400 (730). Network device 400 mayreceive the RRC connection request with an HPA status. In this case, UE110-2, which was in an Idle RRC state, temporarily elevates the priorityof the RRC connection and the bearer channels, and transmits the RRCconnection request with elevated priority (e.g., HPA) status. Networkdevice 400, upon receiving RRC connection request with elevated prioritystatus, admits UE 110-2 and temporally elevates the normal/public userto elevated priority status (e.g., HPA) prior to establishing a callsession (740).

FIGS. 8A-8B are diagrams showing exemplary message flows within awireless communication system 200 and/or 300 for RAN implemented pagingof a UE having non-elevated priority during wireless network congestion.The message flow diagrams show network components which may correspondto both LTE and 5G network standards. As noted above, the LTE componentsare shown with the label “2XX” and the 5G components are shown with thelabel “3XX.” For example, as shown in FIGS. 8A-8B, the base stationelements are shown as “eNode 220/gNode 310,” the mobility managers areshown as “MME 250/AMF 320,” etc.

In FIG. 8A, flow diagram 600 initially shows UE 110-1 and UE 110-2 ashaving completed an attachment and registration procedure and are bothin an RCC Idle state (802). In the embodiment shown in FIG. 8A, UE 110-2is associated with a non-HPA status (i.e., a non-elevated or “normal”priority status), and UE 110-1 is associated with an HPA status (i.e.,an elevated priority status). UE 110-1 may originate a priorityconnection to UE 110-2 during a period of congestion on the RAN (804). Apriority connection request is sent from UE 110-1 to PGW 280/SGW 260 orUPF 330. The connection request may be provided via IMS 140. PGW 280/SGW260 or UPF 330 may then send a downlink data notification to MME 250 orAMF 320 (806). The downlink data notification may also include a messageor signal for a high priority allocation (HPA) and retention priority(ARP) status. MME 250/AMF 320 may generate and send to eNB 220/gNB 310 apaging message with a paging priority indicator (indicating an elevatedpriority), and an s-TMSI value indicating the identity of UE 110-2(808). Upon receiving the paging message (808), eNB 220/gNB 310 maydetect RAN congestion (Block 810), and identify the paging message ashaving a high priority status (812). ENB 220/gNB 310 may send a pagingmessage, along with a paging priority, via RAN 115, to UE 110-2. In anembodiment, the paging priority may be indicated as a parameter in thepaging message having a 1-bit value.

Further referring to FIG. 8B, UE 110-2 may identify the paging priorityindicator and elevate the user priority (816). Subsequently, UE 110-2provides an RRC connection request to eNB 220/gNB 310 having an elevatedpriority status (e.g., HPA) (810). eNB 220/gNB 310 may recognize the UE110-2 as having elevated priority, based upon the parameter in the RRCconnection request, and admit UE 110-2 as an priority user (820). UE110-2 may then be admitted to RAN 115, and a bearer path can beestablished (822). UE 110-2 may then establish priority communicationswith UE 110-1 (824).

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention. For example, while series of blocks have beendescribed with regard to FIGS. 5A, 5B and 7, message flows with regardto FIGS. 6A-6B and 8A-8B the order of the blocks and message may bemodified in other embodiments. Further, non-dependent messaging and/orprocessing blocks may be performed in parallel.

Certain features described above may be implemented as “logic” or a“unit” that performs one or more functions. This logic or unit mayinclude hardware, such as one or more processors, microprocessors,application specific integrated circuits, or field programmable gatearrays, software, or a combination of hardware and software.

In the preceding specification, various example embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, groups or other entities, itshould be understood that such information shall be used in accordancewith all applicable laws concerning protection of personal information.Additionally, the collection, storage, and use of such information canbe subject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various access control,encryption and anonymization techniques for particularly sensitiveinformation.

The terms “comprises” and/or “comprising,” as used herein specify thepresence of stated features, integers, steps or components but does notpreclude the presence or addition of one or more other features,integers, steps, components, or groups thereof. Further, the term“exemplary” (e.g., “exemplary embodiment,” “exemplary configuration,”etc.) means “as an example” and does not mean “preferred,” “best,” orlikewise.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. Also, as used herein, thearticle “a” is intended to include one or more items. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, at a basestation and from a core network, a paging message associated with apriority connection from a first user equipment device (UE) having anelevated priority status, to a second UE having a non-elevated prioritystatus; determining, at the base station, that non-elevated prioritywireless access channels are congested; detecting, at the base station,a priority indicator within the received paging message in response todetermining that the non-elevated priority wireless access channels arecongested; caching, at the base station, an identifier of the second UEin response to detecting the priority indicator in the received pagingmessage; and establishing a wireless connection between the first UE andthe second UE upon verifying that the identifier of the second UE hasbeen cached.
 2. The method of claim 1, wherein determining that thenon-elevated priority wireless access channels are congested comprises:determining, for a non-elevated priority bearer channel, that a trafficthreshold has been exceeded or resources associated with a radioresource control layer have been exhausted or exceeded.
 3. The method ofclaim 2, wherein the establishing a wireless connection furthercomprises: raising the status of the second UE from non-elevatedpriority to an elevated priority; and elevating the non-elevatedpriority bearer channel to a priority bearer channel for a duration of asession between the first UE and the second UE.
 4. The method of claim1, wherein establishing the wireless connection further comprises:forwarding, from the base station, the paging message to the second UE;and receiving, at the base station, a connection request from the secondUE in response to the forwarded paging message.
 5. The method of claim4, wherein establishing the wireless connection further comprises:identifying, at the base station, that the received connection requestfrom the second UE has a non-elevated priority status; determiningwhether the identifier of the second UE has been cached; and admitting,by the base station, the second UE to the wireless connection withelevated priority status in response to determining the identifier ofthe second UE was cached.
 6. The method of claim 5, further comprising:rejecting the second UE in response to determining that the identifierof the second UE was not cached.
 7. The method of claim 1, wherein thefirst UE is associated with a high priority access (HPA) servicecomprising at least one of wireless priority service (WPS), a publicsafety service, a national security service, or an emergencypreparedness service, and the second UE is associated with a normalpriority service.
 8. A network device, comprising: a communicationinterface; and a processor coupled to the communication interface,wherein the processor is configured to: receive, from a core network, apaging message associated with a priority connection from a first userequipment device (UE) having an elevated priority status, to a second UEhaving a non-elevated priority status; determine that non-elevatedpriority wireless access channels are congested; detect a priorityindicator within the received paging message in response to determiningthat the non-elevated priority wireless access channels are congested;cache an identifier of the second UE in response to detecting thepriority indicator in the received paging message; and establish awireless connection between the first UE and the second UE uponverifying that the identifier of the second UE has been cached.
 9. Thenetwork device of claim 8, wherein upon determining that thenon-elevated priority wireless access channels are congested, theprocessor is further configured to: determine, for a non-elevatedpriority bearer channel, that a traffic threshold has been exceeded orresources associated with a radio resource control layer have beenexhausted or exceeded.
 10. The network device of claim 9, wherein uponestablishing a wireless connection, the processor is further configuredto: raise the status of the second UE from non-elevated priority to anelevated priority; and elevate the non-elevated priority bearer channelto a priority bearer channel for a duration of a session between thefirst UE and the second UE.
 11. The network device of claim 8, whereinupon establishing a wireless connection, the processor is furtherconfigured to: forward the paging message to the second UE; and receivea connection request from the second UE in response to the forwardedpaging message.
 12. The network device of claim 11, wherein uponestablishing a wireless connection, the processor is further configuredto: identify that the received connection request from the second UE hasa non-elevated priority status; determine whether the identifier of thesecond UE has been cached; and admit the second UE to the wirelessconnection with elevated priority status in response to determining theidentifier of the second UE was cached.
 13. The network device of claim11, wherein the processor is further configured to: reject the second UEin response to determining that the identifier of the second UE was notcached.
 14. The network device of claim 8, wherein the first UE isassociated with a high priority access (HPA) service comprising at leastone of wireless priority service (WPS), a public safety service, anational security service, or an emergency preparedness service, and thesecond UE is associated with a normal priority service.
 15. Anon-transitory computer-readable medium comprising instructions, which,when executed by a processor, cause the processor to: receive, at a basestation and from a core network, a paging message associated with apriority connection from a first user equipment device (UE) having anelevated priority status, to a second UE having a non-elevated prioritystatus; determine that non-elevated priority wireless access channelsare congested; detect a priority indicator within the received pagingmessage in response to determining that the non-elevated prioritywireless access channels are congested; cache an identifier of thesecond UE in response to detecting the priority indicator in thereceived paging message; and establish a wireless connection between thefirst UE and the second UE upon verifying that the identifier of thesecond UE has been cached.
 16. The non-transitory computer-readablemedium of claim 15, wherein the instructions to determine that thenon-elevated priority wireless access channels are congested furthercause the processor to: determine, for a non-elevated priority bearerchannel, that a traffic threshold has been exceeded or resourcesassociated with a radio resource control layer have been exhausted orexceeded.
 17. The non-transitory computer-readable medium of claim 16,wherein the instructions to establish a wireless connection furthercause the processor to: raise the status of the second UE fromnon-elevated priority to an elevated priority; and elevate thenon-elevated priority bearer channel to a priority bearer channel for aduration or a session between the first UE and the second UE.
 18. Thenon-transitory computer-readable medium of claim 15, wherein theinstructions to establish a wireless connection further cause theprocessor to: forward the paging message to the second UE; and receive aconnection request from the second UE in response to the forwardedpaging message.
 19. The non-transitory computer-readable medium of claim18, wherein the instructions to establish a wireless connection furthercause the processor to: identify that the received connection requestfrom the second UE has a non-elevated priority status; determine whetherthe identifier of the second UE has been cached; and admit the second UEto the wireless connection with elevated priority status in response todetermining the identifier of the second UE was cached.
 20. Thenon-transitory computer-readable medium of claim 18, wherein theprocessor is further configured to: reject the second UE in response todetermining that the identifier of the second UE was not cached.